rename get_columns_by_name
to select
#245
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
"get_columns_by_name" has been annoying me for a while. Someone has even commented that there's no need to note that this API is developer-focused, as with such an anti-ergonomic name, no user would ever consider using it anyway 😄
Then, the following question from a user has prompted me to finally suggest renaming it:
I'm suggesting
select
because it's already kind of a standardised name:select
DataFrame.select
DataFrame.select
select
Q: what about get_column_by_name?
Let's wait until after Thursday's call to discuss this one, depending on the decision that's taken with
Column